com.ibm.pvc.webcontainer.security.AuthEngine removes the pound symbol (#) from users' passwords
 Developers may notice that in versions of Expeditor prior to 6.2.1 fixpack 1 (FP1) that AuthEngine authenticate(String username, String password) implementations removed or truncated passwords at the pound symbol.  This was due to a code defect; however, it has been resolved in Expeditor 6.2.1 fixpack 1 (FP1) and higher.

'Windows requires a digitally signed driver' for CITMDRV Service
Expeditor Clients installed on Windows Vista or Windows 7 may report the above error message during installation.  The error can be disregarded as it does not inhibit product function.  Expeditor 6.2.2 contains changes which will prevent the message from displaying.

Accounts framework does not re-authenticate users after LTPAToken expiration
Currently, the Accounts framework is unaware of LTPAToken expiration.  The LTPAToken by design lacks an expires time, which makes it difficult for the Expeditor platform to perform re-authentication.  Developers and users should be aware that after initial login, a login form may be provided by the application server once the LTPAToken's expiration has been exceeded.

Expeditor clients fail to start on machines which also have HP Quick Test Pro installed
Quick Test Pro creates environment variables which are incompatible with the Expeditor client.  To resolve, set \rcp\deploy\jvm.properties file to write permission (by default it is read-only).  Add the line env.unset.JAVA_TOOL_OPTIONS.  Please note that depending on your Expeditor deployment, two JVM.properties could be used. If you've installed Expeditor with an external JVM, then update the JVM.properties in the /rcp/deploy directory. If you are simply using the 1.6 JVM packaged within Expeditor, update the JVM.properties within the /rcp/eclipse/plugins/com.ibm.rcp.j2se.win32.x86_1.6.0. folder.

javax.net.ssl.keyStorePassword command improperly read
Developers may encounter the following error message if they have updated the key store or key store's password from Expeditor defaults:
The error is due to Expeditor incorrectly reading the javax.net.ssl.keyStorePassword property from either the command line or rcpinstall.properties file.  A defect (APAR IC65248, SPR SJOB7YZE4Q) has been fixed in Expeditor 6.2.1 fixpack 2 which resolves the issue.  For developers unable to upgrade, you may use the java.net.ssl.keyStorePassword property to specify the password.  Note javax becomes java in the property.

Should I use -pluginCustomization or -plugincustomization on the command line
While the Eclipse platform will accept either the camel case pluginCustomization or lower case plugincustomization command line argument, Expeditor requires the lower case plugincustomization argument to be supplied on the command line.

How do I use Portal to deliver settings to clients
See Delivering Managed Settings Using WebSphere Portal.
 
NCI installation fails
Administrators may notice the following messages in the log after a failed NCI installation:
Should you copy the nci folder from the download or DVD media, do not rename the root nci directory to another name.  Either copy nci directly to disk or nest the nci folder within another directory.

The Embedded Browser uses the Microsoft JVM, which causes my web application to fail
If the Microsoft JVM is installed, Internet Explorer will use it rather than an installed Java VM. Note that applets are run with the operating system's JVM - not the JVM that ships with Lotus Expeditor. To resolve, set the Windows System Variable JAVA_PLUGIN_WEBCONTROL_ENABLE to 1. This will force Internet Explorer to use the JVM defined by the Java Plugin rather than the Microsoft VM.